Computer system and control method for computer system

ABSTRACT

In cases where decided that the guaranteed resource capacity for virtual machine cannot be acquired all at one time, the computer system of the present invention decides whether or not resource capacity guaranteed for virtual machine can be continuously acquired by the start of the virtual machine operation, and if decided that the resource capacity can be continuously acquired, the computer system allocates the total acquired resource capacity to the virtual machine deployed on the physical machine.

TECHNICAL FIELD

The present invention relates to a computer system, and a control methodfor a computer system, and relates in particular to a computer systemfor controlling the allocation of resources to virtual machines and amethod for allocating resources to virtual machines.

Along with advances in the information society, there is also a trend toinstall multiple servers in clusters in company information processingsystems and data centers, etc. Moreover, there is also a trend toincrease the number of servers. Furthermore, increasing the number ofservers also increases the labor required for server operationmanagement and consequently leads to a rise in management costs that istoo large to ignore.

Whereupon attention was focused on technology for virtualizing computersin order to boost server operating efficiency. The architecture orsoftware for achieving a virtualized computer operates multiple virtualmachines by the virtualizing of physical resources such as computerprocessors and storage devices. More specifically, the architecture orsoftware logically sub-divides the physical resources, and assigns thesub-divided physical resources to each of the virtual machines. Thevirtualizing software for creating the virtual environment on a computeris known as a hypervisor such as Virtage, VMware, and Hyper-V (all tradenames).

Each of the multiple virtual machines can run an OS or applicationprogram by utilizing the sub-divided resources. Virtual machinestherefore provide the benefit that the physical server is operated moreefficiently and consequently the number of (physical) computers can bedecreased.

A business operation utilizing virtual technology on physical servers isthe server hosting service. The server hosting service is a businessoperation that lends a portion of the physical server to the user for acertain period. The operator of the server hosting service installsmultiple servers in a cluster in a data center, obtains a resourcecapacity matching requests from multiple users for resource allocation,and assigns that resource capacity to the virtual server utilized by theuser.

The user then utilizes the virtual machines assigned with resources as awork-task system. The resource administrator manages the scheduling ofthe resource capacity that will be utilized on the multiple servers inorder to avoid conflicts from the multiple virtual machines seizingresources from one physical computer.

The resource administrator deploys virtual machines on the physicalserver capable of assigning a resource capacity requested by the userprior to the time and date that the user commences usage of thework-task system.

The resource administrator utilizes a management system capable ofuniform management of the multiple virtual environments. This managementsystem is capable of specifying the physical server functioning as thedestination for deploying the virtual machines according to theavailable resource status.

When the resource capacity assigned to the user is inadequate, theresource administrator attempts to adjust the resource capacity amongthe multiple virtual servers based on the order of priority of thecontract and work-task system with the user. However, when the resourceadministrator determines that the resource capacity required by the usercannot acquire, then that information must be swiftly reported to theuser.

Technology of the related art for acquiring resources for the virtualserver is for example the resource control system disclosed in theJapanese Unexamined Patent Application Publication No. 2005-309644.

This resource control system of the related art is featured in operatingthe work-task system, periodically collecting the resource usage statusof the virtual server that dynamically fluctuates according to theassigned resource capacity, calculating the resource capacity requiredby the virtual server usage status, and retrieving the surplus resourcecapacity from the resource assigned to the virtual server.

SUMMARY

The resource control system of the related art measured the availableresource status on the physical computer and attempted to acquireresources for a virtual machine. However, when other virtual machineswere temporarily using the resources, the resource control system wasforced to decide that resources cannot be acquired at that time for thetarget virtual machine. This trend markedly increased when the resourcecontrol system of the related art attempted to provide a large resourcecapacity for the virtual machine all at one time. A surplus resourcecapacity can however be made available for the virtual machine if thetime is equalized and in many cases adequate resources can be acquiredfor the target virtual machine.

In view of the aforementioned problems with the related art, the presentinvention has the object of providing a computer system and a controlmethod for that computer system capable of efficiently allocatingphysical computer resources to physical machines.

A further object of the present invention is to provide a computersystem and a control method for that computer system capable ofallocating physical computer resources to virtual machines byrecognizing that a substantial surplus resource capacity is availableeven if there is a temporary shortage in resource capacity.

In order to achieve the above stated objectives, when judged thatsufficient resource capacity to ensure virtual machine operation cannotbe acquired all at one time, the computer system of the presentinvention decides whether resource capacity required for virtual machineoperation can be continuously acquired prior to startup of the virtualmachines; and if decided that the resource capacity can be continuouslyacquired, the computer system allocates the total acquired resourcecapacity to the virtual machine deployed on the physical computer.

The present invention can therefore provide a computer system and acontrol method for that computer system capable of efficientlyallocating resources of the physical computer to the virtual machine;and can moreover provide a computer system and a control method for thatcomputer system capable of allocating resources to a virtual machine byrecognizing that a substantial surplus resource capacity is availableeven if there is a temporary shortage in resource capacity.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of the hardware of the computer system of thefirst embodiment of the present invention;

FIG. 2 is a block diagram showing the common hardware structure of amanagement computer/server and a physical machine;

FIG. 3 is one example of a virtual machine resource table;

FIG. 4 is one example of a work-task table;

FIG. 5 is one example of a physical computer resource table;

FIG. 6 is one example of a linking table;

FIG. 7 is a flowchart showing the process for generating the resourceacquisition pool in the managed physical computer;

FIG. 8 is a flowchart showing the process for acquiring resources in theresource acquisition pool;

FIG. 9 is a flowchart showing in detail the processing (step 902 in FIG.8) for the resource acquisition unit to gradually acquire the resourcecapacity required by the virtual machine in the resource acquisitionpool;

FIG. 10 is a flowchart showing the processing for distributing resourcesfrom the resource acquisition pool to the virtual machine according tothe order of priority of the work-task system operated by the virtualmachine;

FIG. 11 is a flowchart showing the processing for distributing resourcesfrom the resource acquisition pool to the virtual machine according tothe system structure of the work-task system operated by the virtualmachine;

FIG. 12 is a flowchart showing the processing for managing thatallocation of resources to the virtual machine by way of queues;

FIG. 13 is a flowchart showing the processing for taking over theresource capacity acquired for the virtual machine from the resourceacquisition pool;

FIG. 14 is a flowchart for verifying whether or not the resourcecapacity required for the virtual machine can be acquired prior toexecuting the resource acquisition process;

FIG. 15 is a flowchart showing processing of a request for shifting thevirtual server to another managed physical computer;

FIG. 16 is a flowchart of execution of processing for deleting thevirtual server;

FIG. 17 is a flowchart of the process when removing the virtual serverfrom the physical server when the physical server was set topower-saving mode;

FIG. 18 is a block diagram of the computer system hardware for anotherembodiment of the present invention;

FIG. 19 is a block diagram of the computer system hardware for yetanother embodiment of the present invention;

FIG. 20 is a block diagram of the computer system hardware for stillanother embodiment of the present invention;

FIG. 21 is a block diagram of the computer system hardware for still yetanother embodiment of the present invention;

FIG. 22 is a block diagram of the computer system hardware for stillanother embodiment of the present invention;

FIG. 23 is a block diagram of the computer system hardware for yet stillanother embodiment of the present invention; and

FIG. 24 is a block diagram of the computer system hardware for a furtherembodiment of the present invention.

DETAILED DESCRIPTION

The embodiments of the present invention are described while referringto the accompanying drawings. FIG. 1 is a block diagram of the hardwareof the computer system of the first embodiment of the present invention.This computer system is comprised of multiple physical servers 101, amanagement server 100 mainly for executing resource management of thephysical servers, a monitor terminal 102, and a network 115 mutuallycoupling the aforementioned components.

Virtualizing software is loaded in the physical server 101. Thevirtualizing software is for the purpose of creating multiple computersvirtually capable of operating on the OS of the physical computer.Computers created virtually in this way are called virtual computers orvirtual machines. The virtualizing software sub-divides the resources ofthe physical computer into multiple regions and utilizes these regionsegments to achieve an environment where multiple virtual machines canoperate.

The virtual machines may include servers and may include clients. Theformer are referred to as virtual servers, and hereafter the presentinvention is described based on a configuration where multiple virtualservers are set in the physical server. However, if a virtual machinethen operation is not limited to that of a virtual server and so thevirtual machine may also utilized for the client, serving eitherapplication.

The virtual server utilizing resources that were assigned to it runs onan OS or application almost as if an actual physical server. Theresources may include a processor, memory, storage (hard disk or SSD andso on) and a network, etc.

Multiple virtual machine environments (systems) having different usagepurposes, and OS such as Web servers and mail servers, can be configuredon one physical server. The management server 100 manages allocation ofthe resources of the physical server 101 serving as the managementtarget to the virtual server.

FIG. 2 is a block diagram showing the common hardware structure of themanagement server 100 and the physical server 101. The management server100 and the managed physical server 101 include a hardware structureidentical to that of a general-purpose computer.

The server includes a CPU 600, a main memory device 601, a networkadapter 602, a storage adapter 603, a storage device 604, and a commonbus 605 that mutually connects these components.

A network adapter 602 is connected to the management network 115A. TheCPU 600 is connectable to other servers by way of the network 115A.

The storage adapter 603 is connected to a storage network 115B such asSAN. The CPU 600 may therefore connect to external storage devices byway of the storage network 115B.

A resource management program such as virtualizing software is stored inthe storage device 604 of physical server 101. The virtualizing softwareexecutes processing to pool the resources in a resource pool, andallocate resource capacity from the resource pool to the virtual server.Namely, allocation of resources to the virtual server is performed fromthe resource pool when the virtual server is linked to the resourcepool. The resource acquisition pool 114 described later on is a poolthat utilizes the resource pool for the purpose of acquiring resources.

As shown in FIG. 1, virtualizing software run on the physical server 101constructs a computer environment (system) configured from a resourceacquisition pool 114 for acquiring resources allocated to the virtualserver 113 from a physical server, and a resource control unit 120 toperform resource management processing such as allocating resources fromthe resource acquisition pool 114 to the virtual server 113, andallocating resources to the resource acquisition pool 114.

One example of a parameter for setting or defining the resource capacityallocated to the virtual server 113 or the resource pool is the“guaranteed value”. This guaranteed value is a parameter equivalent tothe guaranteed resource capacity for allocation to the virtual server113 and resource pool. The resources allocated to that virtual server orresource pool are therefore guaranteed within a range of the guaranteedvalues, even if there is a conflict due to a virtual server or resourcepool competing for resources with another virtual server. The guaranteedvalue is one among the resource allocation parameters contained in thevirtualizing software, and is typically called a scheduled value orlower limit value.

The management server 100 executes management and control processing foracquiring the resource capacity needed by the virtual server, and alsoperforms resource management processing such as deciding the physicalserver that will serve as the virtual server deployment destination.

The management server 100 sets a scheduled value serving as a guide forthe resource capacity required by the virtual server. The managementserver 100 sets a physical server containing a resource acquisition pool114 having a resource capacity equivalent to the scheduled value as thevirtual server deployment destination.

When starting up the virtual server 113, the resource control unit 120in the managed physical server executes control to acquire a resourcecapacity equivalent to the scheduled value from the resource acquisitionpool 114 into the virtual server 113. Management of the resourcecapacity is executed based on sub-division of the resource such as thephysical server's processor, memory, or I/O into logical blocks.

The management server 100 controls all of the resource acquisition pool114 and virtual servers 113 in the managed physical server 101 to allowor prohibit acquiring the resource capacity needed for the virtualserver 113. The physical server capable of acquiring the resourcecapacity needed by the virtual server is set as the deploymentdestination of the virtual server. A resource acquisition pool 114 isset into each of the multiple managed physical servers 101.

The CPU 600 in the management server 100 as shown in FIG. 1 executesvarious control and management functions on physical server resourcessuch as a resource control unit 103, a resource acquisition unit 104, awork task monitor unit 105, a resource allocation unit 116, a poolcontrol unit 106, a pool generator unit 107, a virtual environmentmonitor unit 108, a performance information collection unit 109, aconfiguration information collection unit 110, and a placement setterunit 111 by executing management programs stored in the storage device604 implemented via the main memory device 601.

The management server 100 contains a management table holding managementdata required for executing the applicable control and managementfunctions on the storage device 604. The management table containsvirtual server resource table 200, a physical server resource table 400,a work-task table 300, and a linking table 500 for linking the virtualserver with the resource acquisition table.

The resource monitor unit 103 executes upper level resource managementprocessing and coordinated functions on other control units. Theresource acquisition unit 104 executes processing to acquire resourcesallocated to the virtual server 113 in the resource acquisition pool114. The work task monitor unit 105 executes processing to monitor thework-task systems operated by the virtual server 113.

The resource allocation unit 116 is a processing unit that utilizes theresource control unit 120 in the managed physical server 101 to controlallocation to the virtual server 113 of resources managed by themanagement server 100.

The pool control unit 106 is a processing unit that utilizes theresource control unit 120 to control the resource capacity of theresource acquisition pool 114.

The pool generator unit 107 performs processing to generate a resourceacquisition pool 114 in the managed physical server 101. The virtualenvironment monitor unit 108 provides an I/F to control the resourcecontrol unit 115 to the management server 100. The management server 100controls multiple managed physical servers 101 by way of the network115A.

The virtual environment monitor unit 108 accesses all of the processingin the resource acquisition unit 104, the resource allocation unit 116,the pool control unit 106, the pool generator unit 107, the performanceinformation collection unit 109, and the configuration informationcollection unit 110 by way of the virtual environment monitor unit 108to the managed physical server 101.

The performance information collection unit 109 is a processing unitthat collects operating information and performance information on themanaged physical server 101, the virtual server 113, and the resourceacquisition pool 114. This performance information includes the CPUusage rate, memory usage rate, storage capacity, data transfer speedwith storage, network data transfer speed, and resource allocationcapacities from the physical server to the virtual server such as CPUallocation quantity and memory allocation quantity, etc.

The configuration information collection unit 110 is a processing unitfor collecting configuration information on the managed physical server101, the virtual server 113, and the resource acquisition pool 114. Theconfiguration information is information relating to the hardwareconfiguration of the managed physical server 101, the logical systemconfigurations such as the Web3 hierarchical structures, and also thework-task system configurations of those system configurations.

The performance information collection unit 109 and the configurationinformation collection unit 110 each periodically access the processingobject at specified sampling periods, collect information, and recordthe collected information in the management table.

The placement setter unit 111 sets which managed physical server 101 toplace and operate the virtual server 113 for assignment of resources.The placement setter unit 111 is a processing unit for setting thephysical server where the virtual server must be placed.

The virtual environment monitor unit 108 is present inside themanagement server 100; however, the management server 100 can be presentin another physical server that can be accessed by way of the network115. The resource acquisition unit 104 of the management server 100 canfor example in that case also access the managed physical server 101 byway of the virtual environment management unit of the applicablephysical server. The virtual environment monitor unit 108 may alsooperate on the virtual server 113.

Each processing unit of the management server may also access themanaged physical server by way of an I/F (interface) for the resourcecontrol unit 120 without utilizing the virtual environment monitor unit108.

The resource control unit 120 executes control and management processingof the virtual server 113 and resource acquisition pool 114 afterreceiving commands from the management server 100.

The monitor terminal 102 sends input information for managing themanagement server 100 by way of the network 115A, and also receivesinformation on management status that was output from the managementserver 100. The reference numeral 112 denotes the input/output unitcomprised of hardware such as a keyboard and display, and software suchas an interface.

The management user refers by way of the monitor terminal 102 toconfiguration information and performance information for the managedphysical server 101, the virtual server 113, and the resourceacquisition pool 114 that are subject to control (control objects) bythe management server 100. The management user then applies control andmanagement processing to these control objects by way of the managementserver 100.

FIG. 3 is one example of the virtual server resource table 200. Thevirtual server resource table 200 manages the resources of the virtualserver 113 and the resource acquisition pool (abbreviated to “pool” inFIG. 2) 114.

The virtual server resource table 200 contains a virtual server andresource acquisition pool recognition field 201, a physical serverrecognition field 202, an actual allocation resource capacity field 203,a requested resource capacity field 204, an acquired resource capacityfield 205, an acquisition flag field 206, a collection time field 207,and a scheduled acquisition resource capacity field 208.

Information for recognizing the entities (virtual server 113 or resourceacquisition pool 114, resource pools other than the resource acquisitionpool) is recorded in the virtual server and resource acquisition poolrecognition field 201. This recognition information is key informationfor each record in the virtual server resource table.

Information for recognizing the managed physical server 101 where theentity operates is recorded in the physical server recognition field202.

The resource capacity currently allocated to the entity is recorded inthe actual allocation resource capacity field 203.

The resource capacity acquired by the entity is recorded in the acquiredresource capacity field 205. If the entity is the virtual server 113then the acquired resource capacity is a quantity based on an amountequivalent to the previously described guaranteed value of the virtualserver. If the entity is a resource acquisition pool then theacquisition resource capacity is an amount based on the resourcecapacity equivalent to the previously described guaranteed value of theresource acquisition pool.

If a virtual server belongs to the resource acquisition pool, then theguaranteed value of the resource acquisition pool is usually larger thanthe sum of the guaranteed values of virtual servers belonging to theresource acquisition pool. The management server 100 cannot usually seta value exceeding the available resource capacity of the physicalserver, as the guaranteed value in the resource acquisition pool 114.The management server 100 increases the guaranteed value of the resourceacquisition pool within the range of the available resource capacitybased on the current state of the physical server available resourcecapacity that can be measured and acquired.

The resource capacity that the entity requested to the resourceallocation unit 116 for allocation is recorded in the requested resourcecapacity field 204. If the resource capacity of the managed physicalserver 101 is not at a critical level, then the requested resourcecapacity field 204 and the actual allocation resource capacity field 203reach equivalent values.

On the other hand, if the resource capacity of the managed physicalserver 101 is at a critical level, the resource control unit 120 cannotallocate a resource capacity to the entity that meets the requiredresource capacity and so the actual allocated resource capacity mightsometimes be smaller than the required resource quantity. If therequested resource capacity is smaller than the acquired resourcecapacity then the requested resource capacity and the actual allocationresource capacity usually reach equivalent values. Conversely, if therequested resource capacity is the same or larger than the acquiredresource capacity then the actual allocation resource capacity field 203usually does not drop below the acquired resource capacity.

Gigabytes (GB) expressing the memory size and storage capacity arerecorded in the actual allocation resource capacity field 203, therequested resource capacity field 204, and the acquired resourcecapacity field 205 as shown in FIG. 3. However in the case that theresource assigned to the virtual server is a network or processor, thenthe CPU frequency (Hz), disk transfer capacity or network transfercapacity (MB/s, packet quantity/s) is recorded as the resource capacity.If there are plural types of resources, then a combination of themultiple types of resource capacities may be recorded or a valuecalculated from the multiple types of resource capacities may berecorded.

Flag information for allowing the management server 100 to decidewhether or not there is an entity to acquire the resource in order toallocate resources from the physical server to the virtual server isrecorded in the acquisition flag field 206.

To set a pool as the resource acquisition pool, the management server100 records a “true” as the acquisition flag, and records a “false” whennot setting a pool as the resource acquisition pool.

The virtual server is usually the supply destination for the source, soa “false” is usually recorded the acquisition flag since the virtualserver is not the resource supply source. However, if setting thevirtual server as the supply source for the resource then the virtualserver is set to “true.” The virtual server that is the resource supplysource may for example creates a state that receives a simulated loadunrelated to the work task by a special program in, and then assigns aresource acquired based on this simulated load to a virtual server forexecuting work task. The record collection times are stored in thecollection time field 207.

When the performance information collection unit 109 and theconfiguration information collection unit 110 collect information by wayof the virtual environment monitor unit 108 from the resource controlunit 120 of the managed physical server, this collected information isrecorded in the virtual server resource table 200 as an initial recordor as rewritten (refresh) record.

The pool generator unit 107 defines the resource acquisition pool 114and sets a “true” in the acquisition flag field 206 when recording thisresource acquisition pool 114 in the virtual server resource table 200.

The resource capacity scheduled for entity acquisition is stored in thescheduled acquisition resource capacity field 208. The scheduledacquisition resource capacity field 208 stores the requested resourcecapacity acquired by the resource acquisition pool or the resourceacquisition virtual server. The value of the acquired resource capacityfield 205 is gradually increased until reaching the target figure forthe resource capacity to acquire as shown in the scheduled acquisitionresource capacity 208. The scheduled acquisition resource capacity field208 stores a value that is the sum of scheduled values in the resourceacquisition requests corresponding to the resource acquisition pool orthe resource acquisition virtual server.

FIG. 4 is a drawing showing one example of a business/work table 300.The business/work table 300 groups the work-task system from thestandpoint of the work executed by the virtual server 113, and recordsresource management information such as resource allocation information,and resource lending schedule information for each work-task system.

The business/work table 300 contains a work-task field 301, a work-taskpriority level field 302, a requested resource capacity field 303, ascheduled period field 304, a virtual server field 305, and a systemrequirements field 306.

The work-task field 301 stores recognition information for the work-tasksystem. This recognition information is key information for the recordthat is recorded in the table.

Priority level information for the work-task system is stored in thework-task priority level field 302. This information is information setby the administrator according to the degree of importance in thework-task system. The work-task priority level is for example a valueestablished according to the service level or reliability and so onrequired by the work-task system. More specifically, the level ofpriority is low when lending resources in a development environment; andthe level of priority is high in ticket sales systems where a highservice level is required.

In a state where multiple work-task systems are operating in the managedphysical server 101, the resource allocation unit 116 correctlydistributes resources to the multiple work-task systems by allocatingresources in the resource acquisition pool 114 to the virtual servers113 for each work-task, based on the priority level.

The resource capacity requested for the work-task system is registeredin the requested resource capacity field 303. Information on the timescheduled for lending resources from the managed physical server 101 tothe work-task system specified by the work-task field 301 is registeredin the scheduled period field 304.

Information for recognizing the virtual server 113 that configure thework-task system specified in the work-task field 301 is registered inthe virtual server field 305.

The system condition information requested for the work-task systemspecified in the work-task field 301 is registered in the systemrequirements field 306. For example, the condition that the multiplevirtual servers 113 configuring the work-task system must each operateon different managed physical servers 101, or conversely the conditionthat the multiple virtual servers 113 must operate on the same managedphysical server 101 is registered in the system requirements field 306.

The former condition is set in order to enhance reliability assumingthat the hardware in the managed physical server 101 will fail. Thelatter condition is set in order to boost shared usage of the managedphysical servers 101 memory, increase the cache hit rate and speed upthe work-task processing.

The work task monitor unit 105 generates or rewrites (refreshes) thework-task table 300 based on the information that the performanceinformation collection unit 109 and the configuration informationcollection unit 110 collected from the managed physical server.

FIG. 5 is a drawing showing one example of the physical server resourcetable 400. The physical server resource table 400 is a table formanaging the resource usage status of the physical server.

The physical server resource table 400 contains a physical server field401, a total resource capacity field 402, an available resource capacityfield 403, and a non-acquired resource capacity field 404.

Information for recognizing the managed physical servers 101 isregistered in the physical server field 401. This recognitioninformation is key information for each record in the physical serverresource table.

The total size of the resource capacity contained in a certain managedphysical server 101 specified by the physical server field 401 isregistered in the total resource capacity field 402.

Among the resource capacity contained in a certain managed physicalserver 101 specified by the physical server field 401; the unusedresource capacity not assigned even to any of the virtual servers 113 orresource acquisition pools 114, or namely a value in which the totalvalue in the actual allocation resource capacity field 203 (FIG. 3)belonging to the same physical server as the physical server field 401(FIG. 5) subtracted from the total resource capacity field 402, isrecorded in the available resource capacity field 403.

Among the resource capacity contained in a certain managed physicalserver 101 specified by the physical server field 401; the resourcecapacity not acquired in the resource acquisition pools 114 is recordedin the non-acquired resource capacity field 404. This value isequivalent to a value in which the total value in the acquired resourcecapacity field 206 (FIG. 3) belonging to the same physical server as thephysical server field 401 (FIG. 5) subtracted from the total resourcecapacity field 402.

This physical server table 400 is generated or rewritten by the resourcemonitor unit 103 based on the collected information by the performanceinformation collection unit 109 and the configuration informationcollection unit 110.

FIG. 6 is a drawing showing one example of the linking table 500. Thecorresponding relation between the virtual servers 113 and the resourceacquisition pools 114 (abbreviated to “pool” in FIG. 6) supplyingresources to the virtual server is recorded in the linking table 500.The virtual server assigned to the resource acquisition pool is recordedin the linking table 500 at the stage where the placement setter unit111 sets the physical server 101 where the virtual server 113 must bedeployed.

The linking table 500 contains a virtual server field 501 and a resourceacquisition pool field 502. Recognition information for the virtualserver 113 is recorded in the virtual server field 501. Information forrecognizing the resource acquisition pools 114 for assigning acquiredresources to the virtual server 113 specified in the virtual serverfield 501 is registered in the resource acquisition pool field 502.

On the other hand, when the period for utilizing the virtual server hasended, the administrator deletes the virtual server entry from thelinking table. If the resource acquisition pool corresponding to thevirtual server does not also correspond to other virtual servers at thistime, then the administrator deletes that resource acquisition pool fromthe linking table.

FIG. 7 is a flowchart showing the operation of the pool generator unit107 (FIG. 1), or namely the process for generating the resourceacquisition pool 114 (abbreviated to “pool” in FIG. 7) in the managedphysical server 101. The pool generator unit 107 executes discovery byway of the network 115A (FIG. 2) and detects new managed physicalservers 101 if present within the management range (step 701).

The pool generator unit 107 accesses the detected physical server 101,analyzes the software environment in the physical server 101 and decideswhether or not there is a virtual environment within the managedphysical server (step 702).

When the pool generator unit 107 makes an affirmative decision in step702, the unit 107 decides whether or not to set a resource acquisitionpool 114 in the physical server 101 based on performance information andconfiguration information in the managed physical server 101 (step 703).

When the pool generator unit 107 decides in step 703 that there is noresource acquisition pool, the unit 107 provides a resource acquisitionpool 114 create command to the hypervisor (resource control unit 120) ofthe physical server 101 (step 704).

The pool generator unit 107 registers the created resource acquisitionpool into the virtual server resource table 200 (FIG. 3) as a managedobject (step 705). More specifically, the pool generator unit 107generates a new record in the virtual server resource table 200, recordsan identifier for the created resource acquisition pool 114 into thevirtual server field 201, records the managed physical server 101 thatgenerated the resource acquisition pool into the physical server field202, and records a “true” in the acquisition flag field 206. Informationon the resource capacity collected by the performance informationcollection unit 109 is recorded in the actual allocation resourcecapacity field 203 and requested resource capacity field 204. The poolgenerator unit 107 sets the scheduled value in the acquired resourcecapacity field 205.

The pool generator unit 107 terminates the flowchart when the unit 107makes a negative decision in step 702. When decided in step 703 thatthere is a resource acquisition pool, the currently used resourceacquisition pool is set as the managed object (step 706) and theflowchart is terminated.

FIG. 8 is a flowchart showing the operation of the resource acquisitionunit 104 (FIG. 1) or namely is a flowchart of the process for acquiringresources in the resource acquisition pool. The resource acquisitionunit 104 executes the process of the flowchart in FIG. 8 if setting amanaged physical server as the deployment destination for a new virtualserver.

In a state where the virtual server is operating on the physical server,resources must again be acquired for the resource acquisition pool, whenthe resource acquisition unit attempts to assign resources to thevirtual server because the resources from the resource acquisition pool114 have already been discharged to the virtual server 113.

Whereupon the resource acquisition unit 104 sets a scheduled valueserving as the resource capacity required by the new virtual serverbased on the information input from the monitor terminal 102, andcalculates a scheduled value to set in the resource acquisition pool.

The resource acquisition unit 104 acquires a threshold value fordeciding the size of the scheduled value from the specified range of themain memory device 601, and compares the scheduled value with thresholdvalue (step 901).

The resource acquisition unit 104 searches the entity recognition field201 (or virtual server and resource acquisition pool recognition field201) in FIG. 3 when the scheduled value is below the threshold value(No: step 901), sets a scheduled value in an unused resource acquisitionpool 114 where there is no acquired resource capacity, and sends acommand to the resource control unit 120 of this resource acquisitionpool 114. The resource control unit 120 that received this transmittedcommand acquires a resource capacity that is equivalent to the scheduledvalue in the resource acquisition pool 114 (step 906).

The scheduled value is at this time smaller than the threshold value, sothe resource acquisition unit 104 can acquire the resource capacityrequired by the virtual server all at one time in the resourceacquisition pool 114 since the managed physical server 101 hassufficient available capacity to supply a resource capacity equivalentto the scheduled value. Rather than using the threshold value, theresource acquisition unit 104 may compare the available capacity of thephysical server with the scheduled value.

On the other hand, when the resource acquisition unit 104 decides thatthe scheduled value exceeds the threshold value (Yes: Step 901) theresource acquisition unit 104 sends continuous resource acquisitionrequests to the resource control unit 120 for the unused resourceacquisition pool 114 so that a resource capacity equivalent to thescheduled value is gradually acquired over multiple times in theresource acquisition pool 114, (described in detail in FIG. 9: step902).

Conventional server hosting business operators in many cases cannotallocate the required resource capacity to the virtual server all at onetime, however when the resource capacity requested by the virtual serverthat is attempting to deploy at the physical server is small, then themanagement server acquires this capacity all at one time by way of steps901, 902, 906; and when the requested resource capacity is large, themanagement server attempts to reliably acquire the target requestedresource capacity by the time the virtual server starts operating, bycontinuously accumulating the resource capacity that is smaller than therequested resource capacity.

The performance information collection unit 109 and configurationinformation collection unit 110 acquire the resource acquisitionprogress status in the resource acquisition pool from the physicalserver 101, and newly register the information in the actual allocationresource capacity field 203, the requested resource capacity field 204,and the acquired resource capacity field 205.

The acquired resource capacity is newly registered in the actualallocation resource capacity field 203, the requested resource capacityfield 204, and the acquired resource capacity 205 as the acquisition ofresource to the resource acquisition pool 114 gradually progresses.

When acquisition of the target resource capacity for the resourceacquisition pool 114 is complete, a resource capacity equivalent to thescheduled value is registered in the acquired resource capacity 205.

FIG. 3 shows the state prior to allocation of resources to the virtualserver where he pool 1 and pool 3 resource acquisition has ended. Pool 2is in a state prior to resource acquisition after discharge of resourcesto the virtual server.

Next, the resource acquisition unit 104 refers to the acquired resourcecapacity field 205 (FIG. 3) to decide (step 903) if a requested resourcecapacity equivalent to the scheduled value can be acquired for at leastone of the resource acquisition pools (abbreviated to “pool” in FIG. 8).When the resource acquisition unit 104 decides the value can beacquired, the resource acquisition pool 114 in which to deploy thevirtual server is decided.

In step 903 when the resource acquisition unit 104 decides thatacquisition of resources for at least one resource acquisition pool hascompleted, the resource acquisition unit 104 decides on the virtualserver that should be deployed in the physical server for that oneresource acquisition pool. On the other hand, when acquisition ofresources for plural resource acquisition pools has completed, then aspecified resource acquisition pool is set as the deployment destinationfor the virtual server in compliance with a specified selectioncriterion.

The selection criterion is the size of the available capacity (FIG. 5:403) of the physical server for the resource acquisition pool per timebefore and after the requested resource capacity acquisition wascompleted.

The resource acquisition unit 104 subsequently releases the acquiredresource region for a resource acquisition pool not selected as thedeployment destination (step 904), and clears the actual allocationresource capacity field 203, the requested resource capacity field 204,and the acquired resource capacity field 205.

The threshold value is generally set in advance for the resourceacquisition unit 104 by the management user or administrator. However,the resource acquisition unit 104 may set the threshold value accordingto the state that the flowchart in FIG. 8 is executed or the resourceacquisition unit 104 may dynamically change the threshold value via aspecified default value or a threshold setting program according to theavailable resource capacity of the managed physical server (FIG. 4) orthe acquired resource capacity (FIG. 3), etc.

A resource capacity difficult to acquire all at one time may for examplebe calculated as the threshold value based on factors such as the numberof virtual severs per managed physical server, specifications for themanaged physical server, or the available size of the physical server.

Next, the resource control unit 120 for the resource acquisition poolset as the virtual server deployment destination, replies with theacquired resource information to the resource management unit 103 of themanagement server 100 (step 905).

The resource acquisition unit 104 further registers the mutual relationbetween the virtual server 113 and the resource acquisition pool 114 inthe linking table 500. As shown in FIG. 1, besides setting the virtualserver outside the resource acquisition pool 114, the resourcemanagement unit 103 can also set the virtual server within the resourceacquisition pool. The resource management unit 103 can also set anotherresource acquisition pool within the resource acquisition pool. In otherwords, the resource management unit 103 can arrange the resourceacquisition pool in layers.

Executing the process for acquiring resources for multiple physicalservers was described using FIG. 8; however, the management server 100may also attempt acquiring resources by setting the priority in order ofphysical servers having a high probability of acquiring the requestedresource capacity, based on results (history log information in FIG. 3)from monitoring resources collected in the past.

FIG. 9 is a flowchart showing in detail the process (step 902 in FIG. 8)for gradually acquiring the resource capacity requested by the virtualserver in the resource acquisition pool by the resource acquisition unit104.

The resource acquisition unit 104 sets a coefficient value that is thesame as the threshold, or lower than the threshold, adds the coefficientvalue to the guaranteed value in the resource acquisition pool 114 (step1001), gradually increases the guaranteed value in the resourceacquisition pool and sends this value to the resource control unit 120.The resource control unit 120 acquires an added resource capacityequivalent to the difference with the guaranteed value (coefficientvalue) in the resource acquisition pool 114.

This coefficient value may be a fixed value or may be a value calculatedas needed by the resource acquisition unit 104 according to the criticallevel of the physical server or namely the available resource capacity(FIG. 4).

The resource acquisition unit 104 adds a resource capacity equivalent tothe coefficient value in the acquired resource capacity 205 for theresource acquisition pool of the virtual server resource table (FIG. 3),and decides whether or not the value after addition has reached therequired resource capacity (value in scheduled acquisition resourcecapacity 208) (step 1002).

If the decision is negative (not reached resource capacity) then theprocessing subsequently returns to step 1001 after a fixed period oftime has elapsed (step 1003), and the resource acquisition unit 104sends a request to the resource control unit 120 to acquire additionalresource capacity equivalent to the coefficient value.

By repeating steps 1001 through step 1003, the resource acquisition unit104 can continuously acquire a resource capacity for the virtual serverthat must be deployed in the physical server in the resource acquisitionpool 114.

If the resource control unit 104 cannot acquire a resource capacity thatreaches the required resource capacity even after repeating the aboveprocessing a specified number of times, then the administrator notifiesthe user to warn that resources cannot be acquired for the virtualserver.

After deciding from the result in the flowcharts in FIG. 8 and FIG. 9that the resource acquisition pool 114 has acquired the necessaryresource capacity, the placement setter unit 111 decides to deploy thevirtual server in a specified physical server where the resourceacquisition pool 114 is located by the time that the virtual serverstarts operating.

In this deployment process, the resource control unit 120 for thespecified physical server stores the virtual server 113 within theresource acquisition pool 114, and allocates the acquired resourceregion for resource acquisition pool 114 to the virtual server 113. Theresource control unit 120 subsequently transfers the resource capacityof resource acquisition pool 114 to the virtual server 113 by releasingthe virtual server 113 to outside the resource acquisition pool 114. Thereduction in resource capacity of the resource acquisition pool 114 andthe increase in resource capacity of the virtual server are recorded inthe table in FIG. 2.

The resource acquisition unit 104 may adjust the sampling interval ofthe acquired resource capacity for the resource acquisition pool fromthe date that the virtual server is deployed in the physical server. Themanagement server 100 may shorten the sampling intervals if the datethat the virtual server will be deployed in the physical server is nearand may actively acquire resources.

FIG. 10 shows an example of the resource allocation processing by theresource allocation unit 116. FIG. 10 is also a flowchart showing theprocess for distributing resources from the resource acquisition pool114 in the virtual server according to the order of priority in thework-task system operated by the virtual server 113.

The resource allocation unit 116 assigns resources from the sameresource acquisition pool 114 to the multiple virtual servers or inother words detects conflicts or competition for resources among themultiple virtual servers 113 (1101).

Next, the resource allocation unit 116 refers to the work-task table inFIG. 4 and specifies the work-task system to execute by utilizing theresource for which the multiple virtual servers are competing (step1102).

The resource allocation unit 116 next (FIG. 4: 302) acquires thework-task system order of priority (step 1103), and apportions theresource capacity of the resource acquisition pool among the multiplevirtual servers according to the order of priority (step 1104). Theresource allocation unit 116 for example may sequentially distribute therequested resource capacity from the resource acquisition pool of thevirtual server for the work-task system in order of high priority.

The resource allocation unit 116 next sends requests regardingassignment of the apportioned resource capacity to the resource controlunit 120 of the physical server where the virtual server is deployed,and distributes the resource capacity required for each of the multiplework-task system (virtual server) from the resource acquisition pool 114(step 1105).

FIG. 11 shows an example of the resource allocation processing by theresource allocation unit 116. FIG. 11 is a flowchart showing the processfor distributing resources from the resource acquisition pool to thevirtual server according to the system configuration of the work-tasksystem operated by the virtual server 113. The system configuration ofthe work-task system is control or management information relating tothe system requirements field 306 shown in the work-task table in FIG.4.

When deploying plural virtual severs in the computer system, theadministrator searches the work-task system conditions implemented bythe multiple virtual servers such as work-task system conditions for theWeb3 layer system comprised for example from multiple virtual machines,and attempts to acquire the collective resources for the multiplevirtual machines.

In that case, the administrator sets whether to deploy the multiplevirtual servers in different physical servers or deploy the multiplevirtual servers in the same physical server; and moreover sets whetherto acquire resources for the multiple virtual servers from the sameresource acquisition pool or acquire the multiple virtual servers fromdifferent pools. Control is therefore necessary for distributingresources from the resource acquisition pool to the multiple virtualservers according to the work-task system conditions in the virtualserver.

The resource allocation unit 116 acquires system configuration conditioninformation on the work-task system (step 1201). Next, the resourceallocation unit 116 distributes resources (step 1202) or namely theresource capacity acquired in the resource acquisition pool 114 to themultiple virtual servers so as to satisfy conditions for systemstructural information acquired in step 1201, and allocates the resourcecapacity to the virtual server according to the distributed value (step1203).

The system conditions may for example include a system configurationthat places the multiple virtual servers 113 in a separate managedphysical server 101 in order to minimize effects from hardwarebreakdowns and improve reliability. Conversely, the system conditionsmay include a system configuration that places the multiple virtualservers 113 in the same managed physical server 101 with the objectiveof high-speed operation. In this case, high speed operation can beachieved since the memory information is jointly shared and networkcommunications can be copied into the memory.

FIG. 12 shows an example of the resource allocation processing by theresource allocation unit 116. FIG. 12 is a flowchart showing the processfor managing the allocation of virtual server resources by way ofqueues. The resource allocation unit 116 that internally monitors thequeues for queuing the resource allocation request, extracts theallocation request from the resource allocation queue (step 1301), andspecifies the resource acquisition pool 114 containing resource capacityfor the extracted allocation request (step 1302).

Next, among information for managing the virtual server resource table200, the resource allocation unit 116 deducts the requested allocationcapacity (scheduled value) from the values in the acquired resourcecapacity field 205 and the scheduled acquisition resource capacity field208 for the record equivalent to the specified resource acquisition pool114 (step 1303). The resource allocation unit 116 also sets a valuecalculated by deducting the requested allocation capacity (scheduledvalue), into the guaranteed value of the specified resource acquisitionpool 114.

The resource allocation unit 116 next allocates the resource capacity(scheduled value) requested allocation from the specified resourceacquisition pool 114, to the virtual server corresponding to the request(step 1304).

FIG. 13 is a specific example of the resource allocation processing bythe resource allocation unit 116. The flowchart in this figure describesthe processing for handover of the resource capacity acquired from theresource acquisition pool 114 to the virtual server 113.

This handover stores the virtual server 113 in the resource acquisitionpool 114, and next executes the process releasing this virtual server113 from storage.

The resource allocation unit 116 specifies a resource acquisition pool(C) to allocate as the acquired resource capacity corresponding to thevirtual server (A) for new deployment on the physical server, from thecorresponding table 400 (step 1401).

Next, the resource allocation unit 116 adds the requested allocationresource capacity (D) in the virtual server (A) to the resourceacquisition pool (C) scheduled value (step 1402). The resourceallocation unit 116 places the virtual server (A) in the resourceacquisition pool (C) (step 1403).

The resource allocation unit 116 next adds the value of the requestedallocation resource capacity (D) portion to the guaranteed value of thevirtual server (A) (step 1404). The resource allocation unit 116 furtherextracts the virtual server (A) from the resource acquisition pool (C)(step 1405). The resource allocation unit 116 subtracts the requestedallocation resource capacity (D) portion in the virtual server (A) fromthe guaranteed value of the resource acquisition pool (C) (step 1406).

The resource control unit 120 changes the guaranteed allocated resourcehanded over from the resource acquisition pool (C) to the virtual server(A) into a virtual server (A) due to a request from the resourceallocation unit 116. Fluctuations in the resource capacity of theresource acquisition pool (C) and the virtual server (A) are registeredby the resource allocation unit 116 in the resource allocation table200.

In the resource handover from the resource acquisition pool to thevirtual server, the resource allocation unit 116 may synchronize thepool and server, and increase the guaranteed value of virtual server 113while reducing the scheduled value of resource acquisition pool 114, toallow acquisition of resources released from the resource acquisitionpool by the virtual server.

FIG. 14 is a flowchart for verifying whether or not the resourcecapacity required for the virtual machine can be acquired in theresource acquisition pool 114 prior to executing the resourceacquisition process.

The resource acquisition unit 104 simulates the flowchart process inFIG. 9, when attempting to acquire a resource capacity exceeding thethreshold value (FIG. 8) in the resource acquisition pool 114.

To accomplish that action, the resource acquisition unit 104consecutively searches the physical server resource table 400 (FIG. 5)when a resource acquisition request is detected in the resourceacquisition pool (step 1501); and monitors the available resourcecapacity 403 of the physical server (step 1502).

The resource acquisition unit 104 estimates the increase (FIG. 9) inresource capacity per each cycle in the process for consecutivelyacquiring resource capacity in the resource acquisition pool 114 fromthe trend in available resource capacity of the physical server; andpredicts trends in future capacity increases of the resource acquisitionpool 114 (step 1503).

The increase in acquired resource capacity was estimated here fromtrends in the available resource capacity of the physical server;however, the resource acquisition process may instead be actuallyperformed as a trial for several times or for a fixed trial period, andan estimate of the resource capacity acquirable in the future made fromthe value thus obtained.

The resource acquisition unit 104 decides based on the predictionresults whether or not the required resource capacity set as thescheduled value in the resource acquisition pool 114 can be acquired bythe scheduled start time of the virtual server (step 1504).

When the resource acquisition unit 104 decides that the requestedallocation resource capacity cannot be acquired by the scheduled starttime even if the continuous acquired quantity of resource capacity isincreased within the tolerance range, the resource acquisition unit 104displays a warning message on the monitor terminal (step 1505). Theadministrator receives this warning message and can request the user todelay the start of the virtual server or lower the virtual serverguaranteed value. Based on the correction request from the user, themanagement server 100 again executes the process in the flowchart inFIG. 14, and after verifying a positive decision for step 1504 (i.e. canacquire resource by virtual server start time), the administrator canstart actually acquiring the required resource capacity into theresource acquisition pool.

FIG. 15 is a flowchart showing processing of a request to shift thevirtual server 113 to another managed physical server 101. When the poolgenerator unit 107 receives a request from the monitor terminal 102 toshift the virtual server (A) to the managed physical server (D) (step1408), checks the linking table 500, and specifies a resourceacquisition pool (C) that is linked to the virtual server (A) (step1409).

Next, the pool generator unit 107 generates a new resource acquisitionpool (E) set with the scheduled value based on the scheduled value forresource acquisition pool (C) in the managed physical server (D) (step1410).

The pool generator unit 107 further shifts the virtual server (A) to themanaged physical server (D) (step 1411), and deletes the resourceacquisition pool (C) (step 1412).

The pool generator unit 107 also changes the corresponding mapping(linking) to the virtual server (A), from the resource acquisition pool(C) to the resource acquisition pool (E) (step 1413) and records thecontents of this change in the linking table.

Next, the resource acquisition unit 104 executes the process forhandover of the resource capacity equivalent to the scheduled value inresource acquisition pool (E) to the virtual server (A) (step 1414).

FIG. 16 is a flowchart of the deletion process executed in the virtualserver 113. When a request is received to delete the virtual server (A)from the monitor terminal 102 (step 1415), the pool generator unit 107specifies a resource acquisition pool (F) corresponding to the virtualserver (A) (step 1416).

The pool generator unit 107 next deletes the virtual server (A) and alsodeletes the resource acquisition pool (F) corresponding to the virtualserver (step 1417). The pool generator unit 107 deletes thecorrespondence between the resource acquisition pool (F) and the virtualserver (A) from the linking table 500.

The pool generator unit 107 checks the acquisition flag 206 for thetable in FIG. 3, and if the virtual server (described later on) is forallocating resource to the virtual server in the work-task system (flag:true) the pool generator unit 107 do not delete this virtual server.

FIG. 17 is a flowchart showing the removing of the virtual server fromthe physical server when the physical server was set to power-savingmode. When the management server 100 detects from the monitor terminal102, a request to shift the computer system to power-saving mode (step2400), the resource monitor unit 103 specifies a physical server (A)ideal for removing all virtual servers among the multiple managedphysical servers to another physical server (step 2402). One such typeof physical server is physical servers having the lowest operating rate.

The resource monitor unit 103 subsequently searches the linking table500 (FIG. 6) and specifies a resource acquisition pool (C) correspondingto the virtual server (B) in physical server (A) (step 2403).

Next, the resource monitor unit 103 sets a scheduled value for the totalresource capacity of physical server (A) in the resource acquisitionpool (C) (step 2404), and decides whether or not that scheduled valuecan be set in the resource acquisition pool (C) (step 2405).

In step 2405, the resource monitor unit 103 compares the scheduled valuewith the threshold value, and if the scheduled value is lower than thethreshold value the resource monitor unit 103 decides that all scheduledvalues can be set all at one time in the resource acquisition pool. Onthe other hand, when decided that the scheduled value exceeds thethreshold value, the resource monitor unit 103 decides that theguaranteed value for the scheduled value cannot be set all at one timein the resource acquisition pool (C), gradually raises the guaranteedvalue of resource acquisition pool (C) up to the entire resourcecapacity portion of physical server (A). The resource monitor unit 103deletes the guaranteed value for the virtual server (B) that is to beremoved from the physical server (A).

When a scheduled value was set in resource acquisition pool (C) all atone time or when executing step 2406, and the resource capacity from thevirtual server (B) is recovered in the resource acquisition pool (C) byfinally setting the scheduled value in the resource acquisition pool(C), and the resource monitor unit 103 consequently detects there is novirtual server operating on the physical server (A) (step 2406); themanagement server 100 shifts the physical server (A) to a power-savingmode (shutdown mode, etc.). The resource monitor unit 103 searches thevirtual server resource table 200 and can attain step 2406 by confirmingthat there is no virtual server containing an actual allocation resourcecapacity 203 in the physical server (A).

By executing the process in the flowchart in FIG. 17, the managementserver 100 can cluster the virtual server (B) in another physical serverand moreover dynamically shift the physical server (A) to a non-usedstate that does not consume resources and so in that way change thephysical server (A) to a power-saving state.

When clustering the virtual server (B) from the physical server (A) toanother physical server is attempted without recovering the resource inthe resource acquisition pool (C) from the virtual server (B); aso-called “ping pong effect” occurs due to a load equalizing programapplied to the computer system causing the virtual server (B) to moveback and forth between the movement source physical server (A) and theother physical server that is the movement destination.

However, this above described “ping pong effect” can be avoided byrecovering that resource in resource acquisition pool (C) in themovement source physical server (A) of the virtual server (B) even insystem environments where a load equalizing system is operating.

Another embodiment relating to the configuration of the virtual server113 and resource acquisition pool 114 for the managed physical server101 is described next. In the previously described embodiment (FIG. 1)the virtual server 113 is released outside the pool 114 when themanagement server 100 allocates resources from the resource acquisitionpool 114 to the virtual server 113. However, in the embodiment in FIG.18, a configuration is employed that keeps the virtual server 113 placedwithin the pool 114.

In this configuration, the virtual server 113 is kept allocated to theresource acquisition pool 114 so that the virtual server 113 occupiesthe resource acquisition pool 114 resources even if the power to thevirtual server 113 is cut off.

FIG. 19 is a block diagram of the computer system for yet anotherembodiment for the corresponding relation between the virtual server 113and the resource acquisition pool 114. In the computer system of theembodiment of FIG. 1, the multiple virtual servers 113 deployed on thephysical server 101 share the same resource acquisition pool 114.However in the embodiment of FIG. 19, one (each) virtual server 113occupies one pool 114 so that no conflicts between other virtual serversoccur even if a virtual server 113 is set outside the pool 114.

FIG. 20 is a block diagram of still another embodiment of the computersystem of the present invention. In this embodiment, the resourceacquisition pools of the multiple managed servers 101 are clusteredtogether, and resources from the clustered resource acquisition pools114 are allocated to the virtual server. The resource acquisition pools114 are set to span across the multiple managed servers 101.

In the embodiment in FIG. 20, resources can be acquired by pluralmanaged servers 101 in single units even in system environments wherethe virtual server 113 shifts dynamically between plural managed servers101. This embodiment is effective when acquiring a resource on anymanaged servers 101 belonging to a group of plural managed servers 101is needed without specifying a physical server as the deploymentdestination.

FIG. 21 is a block diagram of the computer system for still yet anotherembodiment of the computer system of the present invention. In thisembodiment, the managed physical computer 101 includes a function forthe virtual server 113 to acquire resources on its own instead of usingthe resource acquisition pool 114.

The virtual server 113 includes a load generating unit 117 to generate aload on its own. The load generating unit 117 accepts a request from themanaged server 100, generates a simulated load, and acquires a resourcebased on the simulated load. The load generating unit 117 is itself forexample a loop program. The CPU in the virtual server 113 continuouslyor temporarily executes this program to increase the CPU utilizationrate. The resource allocation unit 120 decides to increase the loadstatus from the CPU utilization rate in the virtual server and allocatesresources to the virtual server.

This embodiment is capable of acquiring resources even in virtualenvironments not employing the resource pool concept.

FIG. 22 is a block diagram of the computer system for still anotherembodiment of the computer system of the present invention. The physicalserver 101 employs a distinctive structure containing a load generatingunit 117, a virtual server 118 that is only assigned to other virtualservers and does not itself utilize resources acquired by generating asimulated load, and a virtual server 113 to accept an allocated resourceand implement the work-task system. The virtual server 113 forwork-tasks and the virtual server 118 for resource acquisition arelinked to each other and registered in the linking table 500.

When handing over resources from the virtual server 118 forresource-acquisition to the virtual server 113 for work-task system, theresource acquisition unit 104 synchronizes both servers by increasing ordecreasing their loads or in other words the former virtual servergradually releases the acquired resource while gradually lowering thegenerated load quantity, and the latter virtual server may then acquireresource capacity equivalent to the released resource by graduallyraising the guaranteed value.

The resource-acquisition virtual server 118 can be understood using thepool as an example. Utilizing the present embodiment allows acquiringresources even in virtual environments within no concept of a resourcepool. The virtual server solely for resource-acquisition is a defaultand may also be deployed in the physical server.

FIG. 23 is a block diagram of yet another embodiment of the computersystem of the present invention. In this structure, the network 115extending from the management server 100 connects directly to the loadgenerating unit 117 of the resource-acquisition virtual server 118.

The resource-acquisition virtual server 118 must here be clamped inorder to prevent dynamic movement to other managed physical servers 101.The virtual server 113 on the other hand need not be clamped relative tothe managed physical server 101.

The resource control unit 120 and the management server need not bedirectly connected by way of the network 115. In the embodiment of FIG.23, one load generating unit 117 for each managed server 101 issufficient. Virtual servers 113 not containing a load generating unit117 are operated on the managed server 101 so conflicts between the loadgenerating unit 117 and work-task systems can be prevented by notoperating the load generating unit 117 on a virtual server 113 that runsthe work-task system.

The virtual server 113 can be easily removed and restored by notinstalling any unnecessary programs on the work-task system run by thevirtual server 113. Moreover, when authentication information for theresource-acquisition virtual server 118 required for making processingrequests to the load generating unit 117 from managed server 100 becomesnecessary, however authentication information for the managed physicalserver 101 is available that quantity is adequate so a small amount ofmanagement information is sufficient. The present embodiment cantherefore acquire resources even in virtual environments not employingthe resource pool concept.

FIG. 24 is a block diagram of the computer system for a furtherembodiment of the computer system of the present invention. In thestructure of this embodiment, the management server 100 directlyconnects to the load generating unit 117 of the virtual server 113 byway of the network 115.

In the embodiment in FIG. 24, there is no need to clamp the relationbetween the virtual server 113 and the managed server 101. The virtualserver 113 may be allowed to dynamically move among the managed servers101. In such cases resources requested from any of the multiple managedservers 101 can be acquired. If the management server 100 for example ismanaging the virtual servers 113 by way of the IP addresses set in thevirtual servers 113, the resource acquisition process can be continuedby continuously applying loads per the load generating unit, even if avirtual server 113 has moved to the second managed server from a firstmanaged server. Resources can in other words be acquired by utilizingthe load equalizing program in managed server 101 while dynamicallyrepositioning the virtual server 113.

In the embodiment of FIG. 24, management information can be minimalsince the management sever 100 need not manage the relation between themanaged server 101 and the virtual server 113. The present embodimentcan moreover acquire resources even in virtual environments notemploying the resource pool concept.

What is claimed is:
 1. A computer system comprising: a plurality ofphysical machines; and a management computer to manage the plurality ofphysical machines, wherein the plurality of physical machines eachinclude: a memory to store the programs to create virtual machines; afirst controller to create virtual machines by executing programs, toallocate resources to the created virtual machines, and to operate theapplicable virtual machines, wherein the management computer includes asecond controller to manage the allocation of resources to the virtualmachine, wherein the second controller sets a physical machine capableof continuously acquiring the resource capacity required by theapplicable virtual machine by the start of the virtual machineoperation, and installs the virtual machine in the applicable physicalmachine, and wherein the first controller of the physical machine wherethe applicable virtual machine is installed, operates the applicablevirtual machine by allocating the required resource capacity to theinstalled virtual machine.
 2. A computer system according to claim 1,wherein the second controller installs the virtual machine in theapplicable physical machine if there is a physical machine capable ofacquiring the required resource capacity all at one time, and if thereis no physical machine capable of acquiring the required resourcecapacity all at one time, installs the virtual machine in a physicalmachine capable of attaining the required resource capacity acquisitionwhile continuously acquiring a resource capacity smaller than therequired resource capacity by the start of the virtual machineoperation.
 3. A computer system according to claim 1, wherein each ofthe physical machines includes a pool to acquire resources to allocateto the virtual machine, and wherein the first controller allocates therequired resource capacity to the virtual machine from the applicablepool.
 4. A computer system according to claim 3 wherein the secondcontroller, sets a parameter equivalent to the required resourcecapacity in the pool, decides whether or not the pool can acquire therequired resource capacity based on the parameter, and installs thevirtual machine in a physical machine containing the pool capable ofacquiring the required resource capacity based on the decision results.5. A computer system according to claim 4 wherein the second controller,compares the threshold value and the parameter, acquires the requiredresource capacity all at one time in at least one of the pools in thephysical machines when decided that the parameter is smaller than thethreshold value, continuously acquires the required resource capacity inat least one of the pools in the physical machines when decided that theparameter is larger than the threshold value, and installs the virtualmachine in a physical machine containing the pool where the requiredresource capacity was acquired.
 6. A computer system according to claim5, wherein the second controller gradually acquires the resource in thepool while gradually increasing the parameter when there is no physicalmachine capable of acquiring the required resource capacity all at onetime.
 7. A computer system according to claim 3, wherein the secondcontroller distributes the resource from the pool to a plurality ofvirtual machines according to the level of priority in the work-tasksystem operated by each virtual machine, when allocating resources tothe virtual machines from the pool.
 8. A computer system according toclaim 3, wherein the second controller distributes the resource from thepool to the virtual machines according to the system configuration ofthe work-task system operated by each virtual machine, when allocatingthe resources to the virtual machines from the pool.
 9. A computersystem according to claim 3, wherein the second controller, when settingthe virtual machine in a physical machine, installs the virtual machinein a physical machine containing a pool that acquired the requiredresource capacity, and releases the resource acquired in the applicablepool when the resource is acquired in the pool of a physical machinewhere no virtual machines are installed.
 10. A computer system accordingto claim 6, wherein the second controller, predicts the increase trendin the resource capacity of the pool, decides whether or not therequired resource capacity can be acquired in the pool by the start ofthe virtual machine operation based on the prediction results, andoutputs the decision results to the administrator.
 11. A computer systemaccording to claim 1, wherein each of the first controllers for thephysical machines, generates its own load, and operates aresource-acquisition virtual machine to acquire resources by utilizingthe applicable load, and allocates the acquired resources from theresource-acquisition virtual machine to the virtual machine deployed bythe second controller so that the applicable virtual machine executesthe work-task system by utilizing the allocated resources.
 12. A controlmethod for a computer system including a physical machine to operate avirtual machine; and a management computer to manage the allocation ofresources by the physical machine to a virtual machine, the methodcomprising: the management computer deciding whether or not theguaranteed resource capacity for the virtual machine can be continuouslyacquired by the start of the virtual machine operation, when a decisionwas made that the guaranteed resource capacity for the virtual machinecannot be acquired all at one time, and when deciding that continuousacquisition by the virtual machine start time is possible, themanagement computer allocating the total acquired resource capacity tothe virtual machine, and installing the applicable virtual machine inthe physical machine.
 13. A management computer for a plurality ofphysical machines, to generate virtual machines, allocate resources tothe generated virtual machines, and operate the applicable virtualmachines, comprising: a controller to manage the allocation of resourcesto the virtual machine, wherein the controller, decides a physicalmachine capable of continuously acquiring the resource capacity requiredby the applicable virtual machine by the start of the virtual machineoperation, installs the virtual machine in the applicable physicalmachine, and allocates the required resource capacity to the applicablevirtual machine installed in the physical machine in order to operatethe applicable virtual machine.
 14. A management computer according toclaim 13, wherein if there is a physical machine capable of acquiringthe required resource capacity all at one time, the controller installsthe virtual machine in the applicable physical machine, and if there isno physical machine capable of acquiring the required resource capacityall at one time, installs the virtual machine in a physical machinecapable of attaining the required resource capacity while continuouslyacquiring a resource capacity smaller than the required resourcecapacity by the start of the virtual machine operation.
 15. A physicalserver comprising: a virtual machine; a pool to acquire a resource; anda controller to allocate the acquired resource from the pool, andoperate the work-task system based on the resource allocated to thevirtual machine, wherein the controller continuously acquires therequired resource capacity for the applicable virtual machine, andallocates the required resource capacity from the applicable pool to thevirtual machine by the start of the virtual machine operation.
 16. Aphysical server according to claim 15, wherein the controller acquiresthe required resource capacity all at one time in the pool when therequired resource capacity is smaller than the threshold value, andacquires the required resource capacity continuously in the pool whenthe required resource capacity is larger than the threshold value.